Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1699

reference
659-tree-1
name
1699
tree-preservation-order

undefined

659-tpo-1
uprn
address-text
point
POINT (-1.006939 50.863151)
geometry
MULTIPOLYGON (((-1.006854 50.863142,-1.006857 50.863159,-1.006869 50.863174,-1.006888 50.863186,-1.006911 50.863194,-1.006938 50.863197,-1.006964 50.863195,-1.006988 50.863187,-1.007007 50.863175,-1.007020 50.863160,-1.007024 50.863144,-1.007020 50.863127,-1.007009 50.863112,-1.006990 50.863100,-1.006966 50.863092,-1.006940 50.863089,-1.006914 50.863092,-1.006890 50.863099,-1.006871 50.863111,-1.006858 50.863126,-1.006854 50.863142)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL